Method for detecting and reporting failures in EPL systems

ABSTRACT

A method for handling failures in an electronic price label (EPL) system which automatically diagnoses failures, and which may additionally automatically contact a support organization. The method includes the steps of transmitting a status request to a communications base station (CBS) and to an EPL by a computer, receiving a status reply from the CBS and the EPL by the computer, comparing the status message to fault data within a fault data file stored within a storage medium by the computer, and determining from the comparison whether a fault in the system has occurred.

This is a Division of application Ser. No. 08/503,144, filed Jul. 17, 1995, now U.S. Pat. No. 5,663,963.

BACKGROUND OF THE INVENTION

The present invention relates to electronic price label (EPL) systems, and more specifically to a method for detecting and reporting failures in EPL systems.

EPL systems typically include a plurality of EPLs for each merchandise item in a store. EPLs typically display the price of corresponding merchandise items on store shelves and are typically attached to a rail along the leading edge of the shelves. A store may contain thousands of EPLs to display the prices of the merchandise items. The EPLs are coupled to a central server from where information about the EPLs is typically maintained in an EPL data file. Price information displayed by the EPLs is obtained from the PLU file.

Component failures in today's EPL systems are often diagnosed by service technicians. The technicians go to the sight of the failure and load And execute diagnostic software, which alerts the technicians of possible causes for the failures. The technicians must then order parts. This method of diagnosing EPL systems is time-consuming and costly. All price changes will have to be stopped during the down time.

Therefore, it would be desirable to provide a system and method for monitoring for EPL failures and for alerting service technicians of possible causes for the failures so that they can bring replacement parts with them to the sight to reduce recovery time and shorten down time.

SUMMARY OF THE INVENTION

In accordance with the teachings of the present invention, a method for detecting and reporting failures in EPL systems are provided. The method includes the steps of transmitting a status request to a communications base station (CBS) and to an EPL by a computer, receiving a status reply from the CBS and the EPL by the computer, comparing the status message to fault data within a fault data file stored within a storage medium by the computer, and determining from the comparison whether a fault in the system has occurred.

The method may also automatically contact a support organization with the diagnosed failure and a recommendation.

It is accordingly an object of the present invention to provide a method for detecting and reporting failures in EPL systems.

It is another object of the present invention to provide a method for detecting and reporting failures in EPL systems which constantly monitors the EPL system for failures.

It is another object of the present invention to provide a method for detecting and reporting failures in EPL systems which suggests causes for the failures.

It is another object of the present invention to provide a method for detecting and reporting failures in EPL systems which automatically alerts service personnel to possible causes for the failures.

BRIEF DESCRIPTION OF THE DRAWINGS

Additional benefits and advantages of the present invention will become apparent to those skilled in the art to which this invention relates from the subsequent description of the preferred embodiments and the appended claims, taken in conjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram of an EPL system;

FIG. 2 is a block diagram of an EPL module;

FIG. 3 is a flow diagram illustrating the failure detection and reporting method of the present invention;

FIG. 4 is a chart of tests performed, purpose of tests, and methods of detection; and

FIG. 5 is a chart of faults monitored, actions, and recommendations.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring now to FIG. 1, EPL system 10 includes computer 12, storage medium 14, communication base stations (CBSs) 15a-d, CBS power supply 16a-b, electronic price labels (EPLs) 18a-d, display 22, printer 23, communications circuitry 24, and noisemaker 25.

Computer 12 executes EPL control software 20 and EPL diagnostic software 30. EPL control software 20 records, schedules, and transmits price changes to EPLs 18a-d through CBSs 15a-d, and receives and analyzes status messages from EPLs 18a-d through CBSs 15a-d. EPL control software 20 also maintains and uses EPL data file 28, which contains item information, identification information, item price verifier information, and status information for each of EPLs 18a-d. Computer 12 may include one or more communication ports 31a-b.

Storage medium 14 is preferably a fixed disk drive. Storage medium 14 stores fault data file 26, EPL system configuration file 27, and EPL data file 28. EPL system configuration file tells computer 12 how system 10 is configured, i.e., the addresses of EPL system components and there location relative to other components within system 10.

CBSs 15a-d are connected together in series by cables 35a-c. Here, only four CBSs are shown. CBSs 15a-d each include one transmit antenna 37 and up to four receive antennas 38 for transmitting and receiving messages between CBSs 15a-d and EPLs 18a-d. One or more of CBSs may receive power from a single power supply. Here, CBSs 15a-b receive power from CBS power supply 16a, and CBSs 15c-d receive power from CBS power supply 16b.

CBSs 15a-d each include CBS circuitry 39 which controls operation of each CBS. In CBSs 15a-d, circuitry 39 maintains memory-based CBS data 41. Within CBSs 15b-d, CBS data 41 contains error rates of communication between CBS 15a and each of the other CBSs 15b-d. Within CBS 15a, CBS data 41 contains error rates of communication between CBS 15a and computer 12. When CBS 15c is designated a master as explained below, CBS data 41 contains error rates of communication between CBS 15c and computer 12. Excessively high error rates can signal a bad connection in cables 33a-b, or cables 35a-c.

CBSs 15a-d also include a low-noise amplifier (LNA) 45 which amplifies signals receive by CBS receive antennas 38 so that CBS circuitry 39 can better process the information within those signals.

One cause of CBS failure is a failure of LNA 45. To determine whether LNA 45 is faulty (failed or not connected), computer 12 transmits a status message to CBS 15a, CBS 15a transmits the status message to EPL 18a, and EPL 18a transmits a return signal to CBS 15a. If the return signal is not received by computer 12 through CBS 15a, computer 12 determines whether LNA 45 is consuming power above a predetermined minimum power level. If the power level is below the predetermined minimum power level, computer 12 transmits a fault message to support system 32.

The types of information logged within CBS data 41 include the number of messages sent to other CBSs and whether the other CBSs responded. CBS data 41 also keeps track of the number of messages sent to the EPLs and if it `heard` anything of interest or not.

CBS 15a is a master CBS and CBSs 15b-d are slave CBSs. CBS 15a communicates directly with computer 12. An alternate master may also be designated. Here, CBS 15c is shown as an alternate master which communicates directly with computer 12 through cable 33b when CBS 15a is down (not working properly), its communication port 31a is down, or when cable 33a between CBS 15a and computer 12 is down.

EPL interface software 20 primarily includes data scheduler 34 and CBS manager 36. Data scheduler 34 schedules EPL price change messages to be sent to EPLs 18a-d through CBSs 15 and 16.

CBS manager 36 schedules the actual transmission of price change messages to EPLs 18a-d and the reception of status messages from EPLs 18a-d for predetermined time slots.

EPL diagnostic software 30 automatically monitors EPL system 10 for failures, logs failures in fault data file 26, displays failures on display 22, prints failure reports using printer 23, and reports failures and read faults that have been logged in fault data file 26 by other applications to support system 32 using communication circuitry 24.

Storage medium 14 contains fault data file 26 and EPL data file 28.

Communication circuitry 24 transmits failure messages generated by EPL diagnostic software 30 to support system 32. Communication circuitry 24 is preferably a modem, but could also include network circuitry, such as a local area network (LAN) or wide area network (WAN) adapter.

Support system 32 is preferably a computer system with a modem located at the site of an EPL system vendor or EPL system technician.

Noisemaker 25 alerts users of a failure. Noisemaker 25 is preferably coupled to computer 12.

Turning now to FIG. 2, EPLs 18a-d each include battery 40, transmit and receive antenna 42, display 46, memory 47, and EPL circuitry 48. Since there is only one antenna 42, if antenna 42 is broken, the EPL is considered broken or lost (not in the store).

Battery 40 provides power to EPLs 18a-d. A low battery voltage is one cause for EPL malfunction and failure.

Transmit and receive antenna 42 receives price change and status messages from CBS 15a-d. Failure of antenna 42 can cause EPL 18a-d to miss price change requests from EPL control software 20.

Transmit and receive antenna 42 transmits responses to price change and status messages to CBS 15a-d. Failure of antenna 42 can prevent EPL control software 20 from verifying that price changes have been received and displayed by EPL 18a-d.

Display 46 displays price and possibly additional information. Display 46 is preferably a liquid crystal display and includes glass 49. A failure of display 46, which may include a crack in glass 49, prevents EPL 18a-d from displaying price information to customers.

Memory 47 stores price verifier information. Preferably, the price verifier information is a checksum of the displayed price.

EPL circuitry 48 controls the internal operation of EPL 18a-d. A failure within circuitry 48 can cause a total failure of EPL 18a-d.

Turning now to FIG. 3, the operation of EPL diagnostic software 30 is explained in more detail, beginning with START 60.

In step 62, EPL diagnostic software 30 periodically sends an instruction to CBS manager 36 to transmit a status request to CBSs 15a-d and EPLs 18a-d.

In step 64, EPL diagnostic software 30 receives a status reply from CBS manager 36.

In step 66, EPL diagnostic software 30 compares the status message to fault data file 26 and configuration file 27.

In step 68, EPL diagnostic software 30 determines from the comparison whether a fault has occurred. If not, then the method returns to step 62.

If a fault has been detected, EPL diagnostic software 30 displays the fault condition and a recommendation on display 22. Alternatively, EPL diagnostic software may activate noisemaker 25 or cause a printer to print an error message in step 70.

In step 72, EPL diagnostic software 30 notifies store personnel and support system 32 of the problem and sends a support request containing the fault condition and recommendation to support system 32. Notification of support system 32 and store personnel could be in the form of a displayed, printed, or aural message. Preferably, display 22 is used to notify store personnel. The method then returns to step 62 to continue monitoring EPL system 10.

Advantageously, EPL diagnostic software 30 provides immediate and automatic notification of critical component failure to store personnel and to EPL technicians. Notification of non-critical components failure may be delayed.

EPL diagnostic software 30 performs tests which are listed in FIG. 4.

Examples of failures that are monitored and reported by EPL diagnostic software 30 are shown in FIG. 5.

When a fault occurs, the fault may be determined by implementing one or more tests. For example, if a CBS test on all of CBSs 15a-d indicates that all of CBSs 15a-d have failed, the failure may have been caused by any one of a plurality of causes, least probable of which are substantially simultaneous failures of CBSs 15a-d. A failure of serial port 31a is one possible cause, therefore, a port test is performed. If serial port 31a has failed, EPL diagnostic software 30 generates a support request which is sent to support system 32 by communication circuitry 24.

If serial port 31a has not failed, CBS 15a or cable 33a may have failed. A failure of either prevents messages from reaching CBSs 15b-d. To test this cause, CBS 15c is configured as the master CBS and a CBS test is performed on each CBS 15a-d. If CBS 15a passes the CBS test, then cable 33a is the likely cause of failure. EPL diagnostic software 30 generates a support request which is sent to support system 32 by communication circuitry 24.

If CBS 15a does not pass the test, and other CBSs also do not pass the test, a power supply test is performed to determine whether power supply 16a is the cause of the failure. If both CBS 15a and CBS 15b have failed, the power supply test compares the failure of CBSs 15a and 15b to EPL system configuration file 27. Since CBSs 15a and 15b are both powered by power supply 16a, a failure of power supply 16a is the likely cause. EPL diagnostic software 30 generates a support request which is sent to support system 32 by communication circuitry 24.

As another example of how the tests in FIG. 4 can be combined to diagnose faults in FIG. 5, suppose that EPL diagnostic software 30 queries EPLs 18a-d and provides a preliminary indication that one or more of EPLs 18a-d are not working or not in system 10. If only one EPL is down, then the EPL is down or the EPL is not listed in EPL data file 28.

If a plurality of EPLs 18a-d are down, then one of CBSs 15a-d is probably down since it is not probable that a plurality of EPLs 18a-d would fail substantially simultaneously. A CBS test is performed on the CBS associated with the down EPLs. If the CBS is down, EPL diagnostic software 30 generates a support request which is sent to support system 32 by communication circuitry 24.

If the CBS is not down, then only part of the CBS may be down. The transmitter portion of CBS circuitry 39 may be the likely cause. Therefore, a CBS transmit test is performed. If the CBS cannot transmit to its associated EPLs, then EPL diagnostic software 30 generates a support request which is sent to support system 32 by communication circuitry 24.

Although the present invention has been described with particular reference to certain preferred embodiments thereof, variations and modifications of the present invention can be effected within the spirit and scope of the following claims. 

What is claimed is:
 1. A method of handling faults throughout an electronic price label (EPL) system comprising the steps of:sending a status request message to communication circuitry within the system by a computer within the system; wirelessly transmitting the status request message to an EPL within the system by the communication circuitry; wirelessly receiving a status reply message from the EPL by the communication circuitry; sending the status reply message to the computer by the communication circuitry; comparing the status reply message to fault data within a fault data file stored within a storage medium by the computer; and determining from the comparison whether a fault in the system has occurred.
 2. The method as recited in claim 1, further comprising the step of:if a fault has occurred, displaying a description of the fault on a display by the computer.
 3. The method as recited in claim 1, further comprising the step of:if a fault has occurred, printing a description of the fault by a printer coupled to the computer.
 4. The method as recited in claim 1, further comprising the step of:if a fault has occurred, transmitting a description of the fault to a support organization.
 5. The method as recited in claim 4, further comprising the step of:if a fault has occurred, transmitting a recommendation for fixing the fault to the support organization.
 6. The method as recited in claim 1, further comprising the step of:if a fault has occurred, generating an aural alert.
 7. The method as recited in claim 1, further comprising the step of:comparing the status reply message to system configuration data within a system configuration file stored within a storage medium by the computer.
 8. A method of monitoring a transmit antenna within a communication base station in an electronic price label (EPL) system for failure comprising the steps of:transmitting a status request message to the communication base station and to an EPL by a computer; transmitting an answer message containing a transmitted signal level to the computer by the EPL; comparing the transmitted signal level to fault data within a fault data file stored within a storage medium by the computer; determining from the comparison whether the transmitted signal level is below a predetermined minimum transmitted signal level; and if the transmitted signal level is below the predetermined minimum transmitted signal level, transmitting a fault message indicating that the transmit antenna is faulty to a support organization. 